      *      *                   *     *                          *
      **     *                   **   **                          *
      * *    *             *     * * * *          *          *    *
      *  *   *   *****  *******  *  *  *   *****  ******  ******* ******
      *   *  *  *     *    *     *     *  *     * *     *    *    *     *
      *    * *  *******    *     *     *  *     * *     *    *    *     *
      *     **  *          *     *     *  *     * *     *    *    *     *
      *      *   ******    *     *     *   *****  *     *    *    *     *
      *                                                                 *
      *             The guide to BITNET servers and services            *
      *                                                                 *
      *  Volume 2  Number 4                               October 1987  *
      *                                                                 *
       *****************************************************************
      *                                                                 *
      *  Editor:                           Chris Condon  CONDON@YALEVM  *
      *  Assistant Editor:                 Steve Sutter  SUTTER@YALEVM  *
      *  NetMonth Staff Supervisor:        Gary Moss       MOSS@YALEVM  *
      *                                                                 *
       ***  **   ** ****************************************************
      **** ****** *** **  ** *****************     ********* ************
       * ** *  * *  **   **** *************** ***** ***  *  *  **********
      *    **       **  ****** *  *******    ************  **** *********
              *   *  **   ***** ******** *********** ****  *** **********
                    * ** **       ** *  *  ************* ****** *********
              *  ** *** *  * ****     * ************* * *****************
            *        *   * ***  ** ***** **  ********* *    *************
               * *  *   *  *  *  * ******  **  ****** ****** ************
         * * ** *  *  ** *     ************ ******   ********    *** ****
       *        * ** *** * *  ***** **  *******   *************** *******
      * *  ** * *    *   * ***** *** ******* *** *****************  *****
        **  * ** *    *** ******** ** * *** *** ***** **  ***************
         * * *  *******  ** **  *****    * ******** *************    ****
        *** * ** **  *** *** ***************  * ***** * ********** ******
      *********** ***   ***** ***  ******************* *    ***** *******
       *   ****  ********* ****   *********** * *  *   * *** ******** ***
      ****** * *************   *** *** ***********   ********    ****** *
      ******* ********** * *  ****  ***********   ******* ******* ***   *
      **** *   ******   ******  ************* ********** * **** *********
       ** ******** ********** ** **   ********** ********** *************
      ** **** ***   *** ********* **** **    ************* *  ***********
      * *******  *** **    *** **  ***** *********** **** ********  *****
      *****    **** *  **** *** *   *************************************
      ***************** **** ****  ******************* **** *************
      **   *************** ****  ******************** ****** ************
      ******** ******   ****** ************** ********** ****************
       ******** *    ****************************** *********************
     *** ** ***** ********************* *** ****************** **********
    * ******  *  ******************************** ***********************
    * *******************************************************************
   * ********************************************************************
  ***  *****************************************************************

1


   *************************************************************************
  * Contents                                                                *
  ***************************************************************************

  Bitnotes ................................................................ 1


  FEATURES___________________________________________________________________

  The BITNET Bylaws ....................................................... 4


  SERVERS AND SERVICES_______________________________________________________

  New Mailing Lists ...................................................... 15


  DEPARTMENTS________________________________________________________________

  Feedback ............................................................... 18
  Policies ............................................................... 18


  NetMonth is a  network service  publication  distributed free  of charge to
  students and professionals in BITNET and other networks.  This magazine and
  it's  companion  file, BITNET SERVERS, are  the work  of the  Yale Computer
  Center  BITNET  Services  Library  (BITLIB) staff.  The  BITLIB  is a local
  online help  facility designed to  inform  Yale network  users  about  what
  services are available  to them  through BITNET, and  provide  instructions
  and  utilities  for their  proper use.  In publishing  NetMonth  the BITLIB
  staff  members hope  to share the  fruits of their  labor with institutions
  outside of Yale in  order to promote a productive  and enjoyable networking
  environment for everyone. The BITLIB system is now distributed to more than
  thirty educational institutions worldwide.

  BITNET SERVERS is BITNETs  most  complete  and  up-to-date  list of servers
  and services.  It is sent to  NetMonth  subscribers at the same time as the
  magazine.  BITNET SERVERS is dependent  on your support to remain accurate.
  If you know of servers and  services  not  listed  in BITNET SERVERS, or of
  those listed in the file that  are no longer available, please  contact the
  NetMonth staff at BITLIB@YALEVM.

  For information  on  subscribing  to NetMonth  and  BITNET SERVERS, see the
  "Policies" section on the last pages of this issue. Within "Policies" there
  are also instructions for  submitting  articles,  sending  Letters  to  the
  Editor, and printing this file.


  -----------------------------------------------------

  A publication of the Bitnet Services Library          "Because We're Here."
1

                                                                       Page 1


   *************************************************************************
  * Bitnotes                                                       Issue 15 *
  ***************************************************************************


              "When you're knee-deep in alligators, you don't
                worry about who's going to drain the swamp."


  Just after  the September NetMonth arrived  on the newsstands,   I received
  this letter from John  Voigt of Tulane University.   It is  more than self-
  explanatory, so read on:

       I'd like to address a couple of comments made in the last issue
       of NETMONTH (1987SEP).  The following appeared in that issue:

            * Perhaps a  story would  clarify  my frame of mind:
            Once there was  a  file server named TCSSERVE@TCSVM.
            The  server   was  fairly  popular   and  prospered.
            Several months later,   a  Listserv was installed at
            that  node.     Another  few   months  went  by  and
            TCSSERVE  was  installed  as  a  subserver   of  the
            Listserv.  Now, there is no more TCSSERVE.

            * TCSSERVE   lives  no  more:     The   subserver of
            LISTSERV@TCSVM    recently   discontinued   service.
            TCSSERVE was originally a file server, and was later
            moved to Listserv.

       First of all let  me put an end to this  rumor.   The TCSSERVE
       "subserver" (they are actually  called FILELIST's on LISTSERV)
       is still available on LISTSERV@TCSVM.   In addition,  there is
       another "subserver"  there called RFC  which contains  all the
       internet RFC (request for comment)  files in a format suitable
       for IBM users.

       Next I'd like to put this whole situation into a little easier
       to understand  perspective.   TCSSERVE was  originally written
       for two main reasons:   1.   To  help me learn more about REXX
       and IUCVTRAP and 2.  To provide a collection point for several
       mailing list's postings.

       TCSSERVE started out  as a simple mailbox  which subscribed to
       several BITNET and INTERNET mailing  lists.   It would archive
       incoming  mail  from  these   various  lists  into  individual
       notebooks and keep them on a  public disk.   It was originally
       intended to  archive postings from  IBM7171 and  S-COMPUT (two
       mailing lists  I was running  using the old  BITNIC listserver
       code that Ricky wrote).   TCSSERVE ran this way for close to 2
1

                                                                       Page 2


       months,  back  issues of IBM7171  and S-COMPUT  were available
       locally,  and  everyone was happy.    As more and  more people
       subscribed to these  lists,  I received many  requests for the
       archives.   I then kludged in more  code to allow BITNET users
       (with interactive  message capability anyway)  to  request the
       archived notebooks.   Before long,   people started sending me
       other stuff to put on TCSSERVE and next thing I knew my "magic
       mailbox" had become a full-fledged fileserver.

       But all was not roses in TCSVM-land.  TCSSERVE could only talk
       to a user through interactive messages.   Moreover, it was not
       a trivial  task to  make it  smarter.   Remember  that it  was
       processing mail in an attempt to archive several mailing lists
       at  once.    The  extra  logic to  process  commands  sent  in
       mailfiles and  still be able to  detect those mail  items that
       needed to be archived would  have been excessive.   Many users
       were sending  me requests  via mail  to send  them files  from
       TCSSERVE.   Also,   TCSSERVE knew only  one format  - NETDATA.
       BITNET was  evolving and so  was the  internet and mail  to be
       archived by TCSSERVE kept changing  format,  requiring quite a
       bit of maintenance.

       Enter Eric Thomas, saviour of BITNET bandwidth,  riding on his
       great white steed.  With a few blows of his trusty sword - the
       famous  FRECP11 LISTSERV  -  he solves  many  of my  problems.
       First it was just a replacement for the BITNIC LISTSERV.  Then
       it would keep  archives of mailing lists.   (That replaced one
       function of TCSSERVE.)  Soon, file server functions were added
       for  the  notebooks.   It  was  looking  pretty grim  for  the
       TCSSERVE machine.   The  final blow came when  full fileserver
       functions were  added.   TCSSERVE  was converted  over to  the
       LISTSERV fileserver and discontinued.

       Well almost.

       The thing was it just wouldn't die.

       To this  day I still  get at least  2 or  3 mail items  a week
       either sent to  TCSSERVE or sent to me  asking about TCSSERVE.
       Chris:   I think  POPULAR understated the situation  a little.
       :-)   The  thing is  this:   LISTSERV  just provides  too many
       services too  much better than TCSSERVE  to ever go  back.   I
       miss having the  high profile fileserver that  TCSSERVE was as
       much as  the next  guy.   LISTSERV looks  just like  any other
       LISTSERV -  you don't see  all that  other stuff it  is doing.
       TCSSERVE  really stood  out.   I've  thought  about running  a
       TCSSERVE machine that just forwarded  messages to LISTSERV but
       it seems a little silly.

1

                                                                       Page 3


       Thomas Wolfe  told us we  can never go home  - I can  tell you
       TCSSERVE will never come back.

       The  network evolves,   the  tools  evolve.   We  must  evolve
       (however reluctantly) with it.

       John

  No excuses.   I received a notice that  TCSSERVE was no longer running.   I
  sent a  command to  LISTSERV to confirm  this,  but  I apparently  sent the
  command to the wrong server.  I messed up.

  ***

  This month  I have  decided to  temporarily abandon  our regular  format in
  order to make space for our speacial feature:  The BITENT Bylaws.   This is
  the definitve document which explains what BITNET Inc. is and how it is run
  in clear legal language.  About this time last year we printed the proposed
  BITNET Charter; the Bylaws are the final form of that text: a blueprint for
  BITNET.

            *
   *      *     *           Virtually;
     * *  *
            *  *   *                    Chris
        *       *
      * ** *  ** * * *     ** **  *
       * ** *  * *  **   **     **   * * *    **  *  **  *  *
      *    **       **  ****** *  ***   *    ****  ******  * ** ****
              *   *  **   ***** ******** ****    **  ***   *** ********
                    * ** **       ** *  *  ************     * * ** *****
              *  ** *** *  * ****     * ***** ******* * **** *   *******
            *        *   * ***  ** ***** **  ********* *    ***** *******
               * *  *   *  *  *  * ******  **  ****** ****** ************
         * * ** *  *  ** *     ************ ******   ********    *** ****
       *        * ** *** * *  ***** **  *******   *************** *******
      * *  ** * *    *   * ***** *** ******* *** *****************  *****
        **  * ** *    *** ******** ** * *** *** ****   *  ***************
         * * *  ** ****  ** **  *****               *************    ****
        ***       *  *** *** ******* * *****  * ***** * ********** ******
            ***** ***   *           ****************** *    ***** *******
           ****          * ****   ***** ***** * *  *   * *** ******** ***
      ***        ***********   *** *** *  ***** **   ********    ****** *
      ******* ********** * *  ****  ******  *     ******* ******* ***   *
      **** *   ******   ******  *************          * * **** *********
       ** ******** ********** ** **   ****** *** ********** *************
      ** **** ***   *** ********* **** **    ************* *  ***********
      * *******  *** **    *** **  ***** *********** **** ********  *****
       ****    **** *  **** *** *   ************************************
1

                                                                       Page 4


   *************************************************************************
  * The BITNET Bylaws                                                       *
  ***************************************************************************


                                  BYLAWS OF

                                 BITNET, INC.

                         A CORPORATION NOT FOR PROFIT

                              9 Tamarack Circle

                          Skillman, New Jersey 08558


                            **********************


  ARTICLE I - NAME

  The name of the corporation shall  be  BITNET,   INC.   and it is sometimes
  referred to in these Bylaws as "the Corporation."


  ARTICLE II - PURPOSES

  This corporation  is a  non-profit  corporation  organized and operated not
  for pecuniary  profit,   but  exclusively for  charitable purposes,   to be
  achieved  through the  distribution  of its  funds  for  such purposes  and
  particularly for the  purpose of facilitating the  non-commercial  exchange
  of  information    consistent  with  the  academic purposes  of its  member
  degree-granting  institutions of higher education  and its member consortia
  and member  affiliates of  institutions  of  higher  education.     To  the
  foregoing ends   the corporation may take  and hold  by  bequest,   device,
  gift,   grant,  purchase,    lease  or otherwise  any  property,    real or
  personal,   tangible or  intangible   or  any undivided  interest   therein
  without limitation as to value and shall sell,  convey or otherwise dispose
  of such  property and invest,    reinvest  or  deal with the  principal and
  income  thereof in   such manner  as,   in  the judgment   of the trustees,
  will best promote the purpose of the corporation without limitation, except
  such limitations,   if any,   as may be contained in  the instrument  under
  which  such property  is received,   the Certificate of Incorporation,  the
  Bylaws of the corporation or any laws applicable thereto.   The Corporation
  may  do any  other  act  or thing  incidental  to  or connected  with   the
  foregoing purpose  or in  advancement thereof,  but  not for  the pecuniary
  profit or  financial gain of its  trustees or officers except  as permitted
  under the New Jersey Corporations and Associations Not For Profit Law.
1

                                                                       Page 5


  ARTICLE III - BASIC POLICIES

  1.   To  maintain  and promote the maximum inter-institutional connectivity
  possible.

  The founding  and  guiding  principle of  BITNET has  been   to connect all
  the scholars of the world.

  2.   To  provide a reliable, dependable network for new and existing users.


  3.   Control of BITNET must  remain with its academic member institutions.

  BITNET's  philosophy  reflects  its  origins   in the   academic community.
  Any organization,  governance,    or service proposals need   to  safeguard
  academia's strong  controlling interests  in BITNET.


  ARTICLE IV - MEMBERS

  1.   Classes of Members.    The corporation shall have classes of  members.
  The  initial designation   of such  classes and  the  qualifications of the
  members of such classes shall be as follows:

  (a)  Class A Members:  certain  degree  granting  institutions  of   higher
  education.

  (b)  Class B Members:  certain consortia  and  affiliates  of  institutions
  of higher education.

  (c)  Class C Members:  certain non-profit organizations.

  (d)  Class D Members:  certain other organizations.

  2.   Election  of   Members.    The   Board   of   Trustees  will determine
  eligibility for  each Class  or may modify  the number of  classes by rules
  defined from time to time.

  3.   Membership  Representatives.     Each   member   shall  appoint  three
  representatives as follows:

  (a)  BITNET Institutional Representative (BIR)  -  an  individual appointed
  by      the     BITNET      member     institution's  president/chancellor,
  governing body or delagee thereof,  who can speak for overall institutional
  BITNET policy;   typically  a senior-level  manager or   administrator with
  fiscal and/or policy  responsibility  for  computing  at  an  institutional
  level.    This  individual (or  proxy)   will vote  on matters requiring  a
  vote  of  the  BITNET membership,     appoint  the institution's   official
  Technical   Representative    and Information Services Representative,  and
  represent the BITNET member institution in policy and fiscal matters.
1

                                                                       Page 6


  (b)  BITNET Technical Representative (TECHREP) - an individual appointed by
  the member   institution's BITNET   Institutional Representative   who  can
  speak  for  the  status of  all  the  computers connected to BITNET at that
  institution;    typically a  systems  programmer  knowledgeable  about  and
  responsible  for  at  least   one of  the   connected  computers.      This
  individual will   interface with  the   BITNIC  regarding such   things  as
  technical operations,   routing tables,  the  BITNET DATABASE (as  the only
  official  source of database changes),   and various software such  as mail
  user  agents and mail  transfer agents within that institution.

  (c)  BITNET Information Services Representative  (INFOREP)  - an individual
  appointed    by    the    member    institution's    BITNET   Institutional
  Representative  who   is   responsible   for   local  BITNET    information
  services   support;    this   includes dissemination  of information  about
  BITNET  to  end-users  of each BITNET  node at the  institution,  answering
  questions   from  local   BITNET   users,    etc.;   typically   a   senior
  information/user services staff member.   This individual will be the point
  of  contact    between  the   BITNIC's   information   services   and   the
  institution's  user   community  and   will  be   in  ongoing communication
  with BITNIC staff.

  4.   Voting Rights.     Each  Class A and  B member and no  others shall be
  entitled to  one vote on each matter  submitted  to a vote of the   members
  which  vote   shall   be  cast   by  the   official   BITNET  Institutional
  Representative.  Proxies are allowed.

  5.   Termination of Membership.    The  Board  of Trustees,  by affirmative
  vote of two-thirds  of all of the  members of the board,   may  suspend  or
  expel  a  member  for  cause  after  an  appropriate  hearing,  and,   by a
  majority vote of those present at  any regularly constituted meeting,   may
  terminate  the  membership  of   any member  who  becomes   ineligible  for
  membership,   or suspend or  expel any member who  shall be  in  default in
  the  payment of dues  for the period fixed in Article X of these bylaws.

  6.   Resignation.    Any member  may resign by filing a written resignation
  with  the  Secretary,   but such resignation   shall not relieve the member
  so  resigning of   the  obligation to  pay any  dues  assessments or  other
  charges theretofore accrued and unpaid.

  7.   Reinstatement.    On  written   request,   the Board  of Trustees,  by
  the affirmative  vote of two-thirds  of all  of the members  of  the board,
  may  reinstate  such former  member  to membership  on  such terms  as  the
  Board  of Trustees  may  deem appropriate.

  8.   Transfer  of   Membership.    Membership  in this  corporation is  not
  transferable.
1

                                                                       Page 7


  ARTICLE V  - MEETINGS OF MEMBERS

  1.   Annual  Meeting.    An  annual  meeting  of  the  BITNET Institutional
  Representatives  for  the   purpose  of  electing  trustees   and  for  the
  transaction of such  other business as may come before the meeting shall be
  held at a date,  time and place designated by the Board of Trustees.

  2.   Special  Meetings.    Special  meetings  of  the  BITNET Institutional
  Representatives may be called by the  President,   the Board of Trustees or
  by  petition  of  not  less than  one-tenth  of  the  BITNET  Institutional
  Representatives of Class A and B members.

  3.   Notice of Meetings.    Written or  printed notice or notice via BITNET
  stating the place,  day,    and hour (or procedure in case  of meeting  via
  BITNET)  of  any meeting of  BITNET Institutional Representatives shall  be
  delivered   personally   or   by  mail   or   by  BITNET  to   the   BITNET
  Institutional Representatives not  less than  thirty (30)   days before the
  date of  such meeting.    In case of a special meeting  or when required by
  statute or by  these bylaws, the purposes  for which the meeting  is called
  shall be  stated in the notice.

  4.   Quorum.   The members holding one-third (1/3) of the votes that may be
  cast at  any meeting  shall  constitute a quorum  at such meeting.     If a
  quorum  is not  present  at any  meeting  a majority  of  the vote  holders
  present may  adjourn the meeting without further notice.  For a meeting via
  BITNET a quorum will  be judged to exist for each item  of  business if and
  only if one-third (1/3)  of the eligible votes are cast.


  ARTICLE VI - BOARD OF TRUSTEES

  1.   General Powers.   The affairs of the corporation shall be managed by a
  Board of Trustees.

  2.   Number and Qualifications.   The number of trustees shall be   eleven.
  Each   trustee  shall   be  a   BITNET  Institutional  Representative of  a
  Class A or Class  B member.   Each trustee shall hold   office for the term
  following election and until a successor has been elected and qualified.

  3.   Election  and  Tenure  of Trustees.      Trustees shall  be elected to
  three year terms beginning  on the lst day  of January following the annual
  election,  provided however,   that,  in order to  ensure continuity,   the
  initial Board  of Trustees  shall consist  of five   trustees whose   terms
  shall expire  in  January 1988,    two trustees  whose terms  shall  expire
  in  January  1989,  and  four trustees whose terms shall expire  in January
  1990.    Furthermore, of five terms beginning January 1,  1988,  four terms
  shall be for three years and one shall be for one year.

  The  current  Board  of  Trustees will  nominate at  least  two persons for
  each vacancy  to be  filled  at an  annual  election and  communicate  said
1

                                                                       Page 8


  nominations  to the  electorate  at least   eight weeks prior to the annual
  election.    For a period of three weeks following   notification  by   the
  electorate   of  the   Board's nominations,     members of  the  electorate
  may submit  additional  nominations each of  which shall be  supported by a
  minimum of ten petitions from members of the electorate.

  At the  conclusion of the  petition  period,   ballots  will be distributed
  and   shall  be  returned   within  three   weeks  of distribution in order
  to be counted.

  Brief  statements  by   candidates  on   issues  and   experience  will  be
  distributed to all members.

  In  any  election   with  N vacancies,    each  member   of  the electorate
  will have  N votes,     and  the N  candidates with  the  highest number of
  votes will  be declared elected  to the  board.   In years  where different
  terms are  being filled,    candidates with the  highest numbers   of votes
  will  be elected   for  the  longer  terms.    Ties will  be  broken by  an
  electronic runoff vote.

  4.   Regular Meetings.    A regular annual meeting of the Board of Trustees
  shall  be held  within three  months following  the annual  election  at  a
  place designated  by a  majority of  the board  by resolution at least four
  weeks prior to the meeting.

  5.   Special  Meetings.    Special  meetings of  the Board  of Trustees may
  be  called by or  at  the request of the  President  or any three Trustees.
  Such meetings may be  via BITNET or at a site  designated by the  President
  should it  be deemed necessary by the  person or persons authorized to call
  the special meeting that the meeting be held in person.

  6.   Notice.    Notice to Trustees of any meetings of the Board of Trustees
  shall  be given  at least two  weeks previously thereto  should the meeting
  be via BITNET and four weeks previously thereto should the meeting  be held
  in  person.    Notice shall be given by personal delivery,  or sent by mail
  or telegram to each trustee at his address  as shown by the  records of the
  corporation,    or via BITNET.     Any trustee   may  waive notice  of  any
  meeting.     The attendance  of a trustee at any   meeting shall constitute
  waiver  of notice  of such  meeting,   except  where  a  trustee attends  a
  meeting for the  express purpose  of  objecting to  the transaction  of any
  business because the meeting is not lawfully called or convened.

  7.   Open  Meetings.    All  Board   of Trustees  meetings will be  open to
  BITNET  Institutional  Representatives   from  Class   A   and  B  members.
  Meeting announcements  will be  posted via  BITNET to all  three Membership
  Representatives.    Minutes of Board  of  Trustees meetings will  be posted
  electronically after  acceptance  by  the Board  and the   posting  will be
  noted  to  all three  Membership Representatives via BITNET.
1

                                                                       Page 9


  8.   Quorum.    A  majority  of  the Board  of Trustees  shall constitute a
  quorum for the transaction of business at  any meeting of the  board,   but
  if less than  a majority  of the   trustees is present at  any meeting,   a
  majority   of  the trustees   present  may  adjourn the    meeting  without
  further  notice.    For   meetings via BITNET,  a quorum will  be judged to
  exist for each item of business if and only if a majority of trustees vote.

  9.   Manner of Acting.   The act of a majority of the trustees present at a
  meeting at  which a  quorum is  present shall be  the act  of the  Board of
  Trustees,   unless the  act of a  greater  number is required by  law or by
  these bylaws.

  10.   Vacancies.    Any   vacancy  occurring   in the   Board   of Trustees
  shall   be  filled  at   the next  annual   election;    however,   interim
  appointments, until the next annual election,   may be made by the Board of
  Trustees.

  11.   Compensation.     Trustees   as  such shall  not  receive  any stated
  salaries for their services, but by resolution of the Board of Trustees any
  trustee may  be indemnified for  expenses and costs,   including attorneys'
  fees,   actually  and necessarily  incurred by  him in connection  with any
  claim  asserted against him,   by action in court or otherwise,   by reason
  of his being or  having been such trustee,   except in  relation to matters
  as to  which he  shall have  been guilty  of  gross  negligence or  willful
  misconduct in respect of the matter in which indemnity is sought.


  ARTICLE VII - OFFICERS

  1.   Officers:    The   officers of the  corporation  shall be a president,
  one or  more vice-presidents  (the number  thereof to be determined  by the
  Board of  Trustees),  a secretary,   a treasurer,  and such other  officers
  as may be elected in  accordance with the provisions of this article.   Any
  two  or more offices may be held by the same person,  except the offices of
  president and secretary.

  2.   Election and  Term  of Office:     The  officers  of  the  corporation
  shall   be elected  at   their  regular annual   meeting  by  the Board  of
  Trustees.     If the   election of  officers shall  not be  held  at   such
  meeting,     such   election   shall   be  held   as   soon  thereafter  as
  conveniently may be.  New offices may be created and filled at  any meeting
  of the  Board  of  Trustees.     Each  officer shall  hold office   until a
  successor shall have  been duly elected and shall have been qualified.

  3.   Removal:    Any officer elected or appointed  by the Board of Trustees
  may be removed by  the Board of Trustees  whenever in its judgment the best
  interests of the corporation would be served thereby.

  4.   Vacancies:   A vacancy in any office,  because of  death, resignation,
  removal,   disqualification,   or otherwise,    may be filled by the  Board
  of Trustees for the unexpired  portion of the term.
1

                                                                      Page 10


  5.   President:    The  President  shall  be  the  principal  executive  of
  the corporation and shall,  in general,    supervise and control all of the
  business and  affairs of the corporation.    The President shall preside at
  all meetings  of the members and of the Board of Trustees.    The President
  may sign,   with the  Secretary or  any other   officer of  the corporation
  authorized by the  Board of  Trustees,   any  deeds,   mortgages,    bonds,
  contracts,     or other  instruments  that   the Board   of  Trustees   has
  authorized   to  be  executed,    except in  cases  where  the signing  and
  execution thereof shall be expressly delegated by the  Board of Trustees or
  by these bylaws  or by  statute  to  some other  officer  or  agent of  the
  corporation;   and,  in  general,   the President shall  perform all duties
  incident to   the office  of president  and  such  other duties  as may  be
  prescribed by the Board of Trustees from time to time.

  6.   Vice-President:   In the  absence  of the President or in event of the
  President's  inability or refusal to  act,   the VicePresident or,   in the
  event there be more than one Vice-President,  Vice-Presidents in the  order
  of their election  shall perform the duties of the President,  and when  so
  acting,    shall  have  all  the  powers of  and  be  subject  to  all  the
  restrictions on the President.  Any Vice-President shall perform such other
  duties as  from time to  time may be  assigned by  the President or  by the
  Board of Trustees.

  7.   Treasurer:    The  Treasurer shall have charge and custody of  and  be
  responsible  for all  funds  and  securities  of  the corporation;  receive
  and give receipts for  moneys due and payable to the   corporation from any
  source  whatsoever,   and   deposit all  such moneys  in  the  name of  the
  corporation in   such banks,   trust  companies,  or other  depositories as
  shall be selected by the Board of Trustees;   and, in general,  perform all
  the duties  incident to the  office of treasurer  and such other  duties as
  from time  to time  may be  assigned by the  President or  by the  Board of
  Trustees.

  8.   Secretary:    The  Secretary shall keep the minutes of the meetings of
  the members and  of the Board  of  Trustees in  one or more books  provided
  for that purpose;   see that all  notices are duly given in accordance with
  the provisions of these bylaws or as required by law;   be custodian of the
  corporate records and of the seal of the  corporation and see that the seal
  of the corporation is affixed to all documents,  the  execution of which on
  behalf  of  the  corporation   under  its  seal   is  duly  authorized   in
  accordance with the  provisions of these bylaws;    keep a  register of the
  post office  and  BITNET addresses  of  each  member and   trustee,   which
  shall be  furnished to the Secretary  by  such member  and trustee;  and in
  general,   perform  all duties  incident to   the office  of secretary  and
  such   other  duties  as   from time   to   time may   be  assigned by  the
  President or by the Board of Trustees.
1

                                                                      Page 11


  ARTICLE VIII - COMMITTEES

  1.   Committees  of Trustees:     The  Board  of Trustees,    by resolution
  adopted by   a majority  of the  trustees  in  office,   may  designate and
  appoint one or more committees,  each of which shall consist of two or more
  trustees,   which committees,   to the  extent provided in said resolution,
  shall have  and exercise  the authority  of the  Board of  Trustees in  the
  management of the corporation;  but the designation of  such committees and
  the  delegation  thereto of  authority shall  not operate  to relieve   the
  Board  of  Trustees,   or  any  individual  trustee of  any  responsibility
  imposed on it or him by law.

  2.   Other Committees:    Other  committees   not having and not exercising
  the  authority  of   the   Board  of  Trustees  in  the  management of  the
  corporation may  be designated by  a  resolution adopted by  a majority  of
  the  trustees present  at a  meeting at which a quorum is present.   Except
  as otherwise provided  in such resolution,  members of  each such committee
  shall be  duly appointed  representatives of  members of  the  corporation,
  and the  President of  the corporation shall  appoint the  members thereof.
  Any member thereof  may  be removed  by the  person  or  persons authorized
  to appoint  such member whenever in   their judgment the best  interests of
  the corporation shall be served by such removal.

  3.   Term of  Office:     Each  member  of  a  committee  shall continue as
  such until  his  successor  is appointed,    unless the  committee shall be
  sooner terminated,    or unless  such member  shall cease  to qualify  as a
  member thereof.

  4.   Chairman:   One member of a committee  shall be appointed chairman  by
  the person  or  persons  authorized to  appoint  the members thereof.

  5.   Vacancies:  Vacancies in the membership of any committee may be filled
  by appointments  made  in the  same manner as provided  in the case  of the
  original appointments.

  6.   Quorum:   Unless otherwise  provided in the resolution of the Board of
  Trustees designating  a  committee,    a majority  of the  whole  committee
  shall constitute  a   quorum  and  the act   of  a majority of  the members
  present at a  meeting at which a quorum  is present shall be the act of the
  committee.

  7.   Rules:    Each  committee  may  adopt  rules  for  its  own governance
  not  inconsistant  with these  bylaws  or  with  rules adopted by the Board
  of Trustees.
1

                                                                      Page 12


  ARTICLE IX - CONTRACTS, CHECKS, DEPOSITS AND FUNDS

  1.   Contracts:     The  Board  of Trustees  may authorize  any officer  or
  officers,    agent  or  agents of  the  corporation,    in addition  to the
  officers so authorized   by these bylaws,   to enter into  any  contract or
  execute and deliver  any  instrument  in the name of and  on behalf of  the
  corporation,   and such  authority may be  general or  confined to specific
  instances.

  2.   Checks,   Drafts  or  Orders for  Payment:    All  checks, drafts,  or
  orders  for  the  payment  of  money,    notes,     or  other evidences  of
  indebtedness issued  in  the name of   the corporation shall be  signed  by
  such officer or officers,  agent  or agents of the corporation and in  such
  manner as shall from time  to time be determined by resolution of the Board
  of  Trustees.   In  the  absence of  such determination  by  the  Board  of
  Trustees,   such  instruments shall  be  signed  by  the  Treasurer or   an
  Assistant  Treasurer and countersigned   by  the  President  or    a  Vice-
  President  of  the corporation.

  3.   Deposits:     All   funds  of  the  corporation   shall  be  deposited
  from  time to time to  the credit of the  corporation in such banks,  trust
  companies, or other depositories as the Board of Trustees may select.

  4.   Gifts:   The Board of Trustees may accept on behalf of the corporation
  any contribution,  gift,  bequest,   or device for the general purposes, or
  for any special purpose, of the corporation.


  ARTICLE X - FEES

  1.   Fees:   The  Board  of  Trustees  may determine  from time to time the
  amount  of  initiation fee,   if  any,   and  annual  fees payable  to  the
  corporation by members of  each class.    Fees  are to remain as low and as
  independent of usage as  possible to  encourage  the widest possible use of
  the  network.     The  corporation  is committed  to  minimizing  fees  and
  maximizing service.  Fees may not be raised more  than 5%  annually without
  majority approval  of the  BITNET Class A and B members.

  2.   Payment of Fees:  Fees shall be payable in advance of the first day of
  the corporation's fiscal year.  The first year's dues of a new member shall
  be prorated  from the  first day of the month in   which  such  new  member
  is  elected  to  membership   for  the remainder of the fiscal  year of the
  corporation.

  3.   Default and Termination of Membership:   When any member of any  class
  shall  be  in  default in the  payment of  fees  for a period   of  two (2)
  months,    his  membership may  thereupon  be  terminated by  the Board  of
  Trustees  in the  manner provided  in Article IV of these bylaws.
1

                                                                      Page 13


  ARTICLE XI - MISCELLANEOUS

  1.   Books and Records:   The  corporation shall  keep correct and complete
  books  and  records  of   account  and  shall  also   keep  minutes of  the
  proceedings  of  the  annual  and  any  special  meetings of   the   BITNET
  Institutional   Representatives,   the  Board  of Trustees,  and committees
  having any of the authority of the Board of Trustees;    and shall  keep at
  the principal  office a  record giving  the  names  and  addresses  of  the
  BITNET  Institutional Representatives entitled to   vote.    All  books and
  records  of  the  corporation   may    be   inspected    by   any    BITNET
  Institutional Representative,  or agent or  attorney for any proper purpose
  at any reasonable time.

  2.   Fiscal Year:   The fiscal  year of the  corporation shall begin on the
  first day of July and  end on the last day of June in the following year.

  3.   Corporate Seal:     The  Board  of Trustees shall  provide a corporate
  seal.

  4.    Waiver of Notice:  Whenever any notice is required to be given  under
  the  provisions of  the New  Jersey Corporations  and Associations Not  for
  Profit  Act or under  the provisions  of the articles of  incorporation  or
  the bylaws for  the corporation,  a waiver thereof in writing signed by the
  person or persons  entitled to such notice,   whether before  or  after the
  time stated  therein,  shall  be deemed  equivalent to  the giving  of such
  notice.


  ARTICLE XII - AMENDMENTS

  1.   Power    of   Members    to   Amend    Bylaws    or   Certificate   of
  Incorporation:    The  Bylaws  or  Certificate  of  Incorporation  of  this
  corporation may be amended, repealed,   or added to,   or new Bylaws may be
  adopted upon  initiation by  either the  Board of Trustees or  by  petition
  of 20%  of   members  with  voting rights,    and   by  affirmative vote of
  two-thirds (2/3)   of the  members with  voting rights who  return  ballots
  at a meeting (including  a meeting via BITNET) duly called for the purpose,
  according to the Certificate of Incorporation or Bylaws.


  CERTIFICATE AUTHENTICATING ADOPTION OF BYLAWS OF BITNET, INC.

  I, Leland H. Williams, do herby certify that:

  1.   I am  the duly elected and  acting Secretary of BITNET,   INC.,  a New
  Jersey corporation not for profit.

  2.   The   foregoing   bylaws,    consisting   of    ten   (10)      pages,
  constitute the  initial  bylaws of  the corporation  as duly adopted   by a
1

                                                                      Page 15


  Unanimous Consent  of the Trustees of  BITNET,  INC.   in Lieu  of Meeting,
  Dated  July  30,   1987.     These  bylaws  have  been determined  by   the
  Executive  Committee   of  BITNET,    an  unincorporated association, which
  Executive Committee has now become the  Board of Trustees of BITNET,  Inc.,
  to be wholly  consistent with the BITNET Charter adopted  by the membership
  in November 1986,  and required in  order  to  operate  the corporation  in
  accordance  with  the principles  of  said  Charter,    such  incorporation
  having  been determined to be necessary to carry out the purposes agreed by
  the members.

  In  witness  whereof,    I  have hereunto  subscribed  my  name and affixed
  the seal of the corporation this 30th day of July, 1987.


   *************************************************************************
  * New Mailing Lists                                                       *
  ***************************************************************************

  FASTBUSL

  News and information list for those who are, or intend to, be involved with
  FASTBUS,   a standardised  modular  32-bit wide  data-bus  system for  data
  aquisition,  data processing  and control,  used mainly by  the High Energy
  Nuclear  Physics   community.    FASTBUS  is  an   international  standard,
  recognised by the IEC, ANSI and IEEE (STD 960-1986) and is freely available
  for use by any profit or non-profit organisation.

  To  subscribe,   send the  following  command  via interactive  message  to
  LISTSERV@CANADA01:

     SUBSCRIBE FASTBUSL Your Full Name

  If you are unable to send interactive messages, you can send the command as
  the only line of a mail message to the LISTSERV.

  Coordinator: Robert G. Skegg 


  FREEMACS

  Mailing list for Freemacs, the PD (actually copylefted) programmable editor
  for the IBM-PC and Z-100.

  To  subscribe,   send the  following  command  via interactive  message  to
  LISTSERV@CLVM:

     SUBSCRIBE FREEMACS Your Full Name

  If you are unable to send interactive messages, you can send the command as
  the only line of a mail message to the LISTSERV.

  Cordinator: Russell Nelson 
1

                                                                      Page 16


  GAMEMASTERS

  Gamemasters is a  more or less daily  digest on topics related  to computer
  moderated  or assisted  role play  gaming.   Topics  include languages  for
  adventure game writing, distributed gaming issues, rule systems, player co-
  operation semantics, user interfaces, new software announcements.  Requests
  for help with puzzles and war stories (eg,   "How do you kill the dragon in
  Adventure?")  ARE NOT WELCOME,  but that's about all.   Gamemasters and the
  old SMAuG mailing list have been merged.


  To  subscribe,   send the  following  command  via interactive  message  to
  LISTSERV@UTCVM:

     SUBSCRIBE GMAST-L Your Full Name

  If you are unable to send interactive messages, you can send the command as
  the he first line of a mail message to the LISTSERV.

  Moderator: Ron Fischer 


  GWMON

  Originally created  as a list  to discuss  the development of  a monitoring
  suite for  gateways,  currently expanded to  a discussion group  for issues
  related to monitoring and managing networks and internetworks.

  All requests to be added to or deleted from this list, problems, questions,
  etc., should be sent to GWMON-REQUEST@SH.CS.NET.

  Coordinator: Craig Partridge 


  INFO-ENCORE@CS-GW.D.UMN.EDU

  Mailing list  for users of the  Encore MultiMax computers and  Encore Annex
  terminal servers.

  All requests to be added or  deleted from this list,  problems,  questions,
  etc., should be sent to INFO-ENCORE-REQUEST@CS-GW.D.UMN.EDU.

  Moderator: Dan Burrows 


  PHYS-L

  This  forum is  designed for  teachers  of college  and university  physics
  courses.   Particular topics of interest include using Bitnet itself as the
1

                                                                      Page 17


  primary medium for the delivery of university courses,  innovative teaching
  laboratory experiments,   and the use of  micros in the  physics classroom.
  The list is open for public subscription.

  To  subscribe,   send the  following  command  via interactive  message  to
  LISTSERV@UCF1VM:

     SUBSCRIBE PHYS-L Your Full Name

  If you are unable to send interactive messages, you can send the command as

  the only line of a mail message to the LISTSERV.

  Coordinator: Dick Smith 


  SF-WRITERS

  The SF Writers Group exists for two purposes:

  1.   To give  people interested in writing Science  Fiction,  Fantasy,  and
  related  genres  professionally   a  support  group  of   peers  for  where
  information can  be shared and  discussions of the  task of writing  can be
  carried on.

  2.   To create an environment where Works  In Progress can be passed around
  and criticized so  that the author can  find the weak spots  and polish the
  manuscript into a sellable work.

  Membership is  open to  anyone who  has in  interest in  writing SF/fantasy
  regardless of  previous experience or published/unpublished  status.   Send
  any questions to WRITERS-REQUEST%SAMBATION@BELLCORE.COM.

  Coordinator: Brian Yamauchi 


  UPORT

  Mailing list for discussion of MicroPort UNIX.

  All  requests to  be added  or to  be  deleted from  this list,   problems,
  questions, etc. should be addressed to UPORT-REQUEST@GATEWAY.MITRE.ORG

  Coordinator: Mike Louden 


  URUSEI YATSURA

  Mailing list for Urusei Yatsura fans.
1

                                                                      Page 18


  All requests to be added to or deleted from this list, problems, questions,
  etc., should     be     sent     to     URUSEI-YATSURA-REQUEST%PANDA@SUMEX-
  AIM.STANFORD.EDU.

  Coordinator: Mark Crispin 


   *************************************************************************
  * Feedback                                                                *
  ***************************************************************************

  Date:     Tue, 13-OCT-1987 16:59 EST
  From:     Steve Wadlow 

  Chris,

   Well..  I  just finished  reading your latest  NetMonth,  and  I am  a bit
  surprised by the whole big deal about Bitnet possibly going to TCP/IP.   Is
  there anywhere where I can get more info on the possible network structure?
  I have a  number of vaguely feasible  ideas as to how  things *might* work,
  but I'm not sure...  One addedum to the article, is that the CMU-TEK TCP/IP
  code  is now  available  for  free distibution,   and  is  (in my  opinion)
  considerable better than the wollongong software.    I can get more info on
  this if you like...

                                          Steve Wadlow


   *************************************************************************
  * NetMonth Policies                                                       *
  ***************************************************************************

  * Subscribing to NetMonth and BITNET SERVERS:

  VM users can be added to the mailing list by issuing the following command:

      TELL LISTSERV AT MARIST SUBSCRIBE NETMONTH Your_full_name

  VAX/VMS users can subscribe in a similar way:

      SEND LISTSERV@MARIST SUBSCRIBE NETMONTH Your_full_name

  If you cannot send messages in this way, you can send the following command
  as the first line of a mail file to LISTSERV@MARIST:

      SUBSCRIBE NETMONTH Your_full_name
1

                                                                      Page 19



  Arpanet users may use this method, but must address the mail to:

      LISTSERV%MARIST.BITNET@WISCVM.WISC.EDU

  A subscriber  can delete  him/herself  from  the mailing  list  by  sending
  LISTSERV@MARIST the UNSUBSCRIBE NETMONTH command.

  * Letters to the Editor:  If you have questions  or  comments  about BITNET
  or  NetMonth  that  you  would  like  printed  here,  mail  your l etter to
  BITLIB@YALEVM.  Make  sure that you  specify  in  the "Subject:"  header or
  somewhere in the letter that it is for the  NetMonth  letters  column. This
  doesn't mean that your letter will be printed, but it helps.

  * Article Submissions: The only requirements for NetMonth articles are that
  they be informative,  interesting, and  deal with  BITNET  services (or any
  other  good BITNET  related topics).  The  editor  will  inform  you of any
  changes to your writing and will submit them  for your  approval, deadlines
  permitting.  Send your articles to BITLIB@YALEVM.

  * Printing this file:  VM users can print this file by  first copying it to
  NETMONTH LISTING and  then printing  the new file.  This will  allow  page-
  breaks and other formatting to be understood by your printer.

  ---------------------------------------------------------------------------

  A publication of the Bitnet Services Library          "Because We're Here."